Research
Security News
Malicious npm Packages Inject SSH Backdoors via Typosquatted Libraries
Socket’s threat research team has detected six malicious npm packages typosquatting popular libraries to insert SSH backdoors.
music-metadata
Advanced tools
The music-metadata npm package is a powerful tool for parsing and extracting metadata from audio files. It supports a wide range of audio formats and provides detailed information about the audio file, including tags, format, and technical properties.
Extract Basic Metadata
This feature allows you to extract basic metadata from an audio file, such as title, artist, album, and genre. The code sample demonstrates how to use the `parseFile` method to read and log metadata from an MP3 file.
const mm = require('music-metadata');
const fs = require('fs');
async function getMetadata(filePath) {
try {
const metadata = await mm.parseFile(filePath);
console.log(metadata);
} catch (error) {
console.error(error.message);
}
}
getMetadata('path/to/audio/file.mp3');
Extract Format Information
This feature allows you to extract format information from an audio file, such as the container type, codec, sample rate, and bit rate. The code sample demonstrates how to use the `parseFile` method to read and log format information from an MP3 file.
const mm = require('music-metadata');
const fs = require('fs');
async function getFormatInfo(filePath) {
try {
const metadata = await mm.parseFile(filePath);
console.log(metadata.format);
} catch (error) {
console.error(error.message);
}
}
getFormatInfo('path/to/audio/file.mp3');
Extract Technical Properties
This feature allows you to extract technical properties from an audio file, such as duration, number of channels, and bit depth. The code sample demonstrates how to use the `parseFile` method to read and log technical properties from an MP3 file.
const mm = require('music-metadata');
const fs = require('fs');
async function getTechnicalProperties(filePath) {
try {
const metadata = await mm.parseFile(filePath);
console.log(metadata.common);
} catch (error) {
console.error(error.message);
}
}
getTechnicalProperties('path/to/audio/file.mp3');
The node-id3 package is focused on reading and writing ID3 tags in MP3 files. It provides a simpler interface for handling ID3 tags compared to music-metadata, but it is limited to MP3 files and does not support other audio formats.
The musicmetadata package is another tool for extracting metadata from audio files. It supports a variety of audio formats and provides similar functionality to music-metadata. However, it is less actively maintained and may not support the latest audio formats and tags.
The id3js package is a JavaScript library for reading ID3 tags from MP3 files. It is designed to work in both Node.js and browser environments. While it offers similar functionality to music-metadata for MP3 files, it does not support other audio formats.
Stream and file based music metadata parser for node.
Audio format | Description | Wiki | |
---|---|---|---|
AIFF / AIFF-C | Audio Interchange File Format | :link: | |
AAC | ADTS / Advanced Audio Coding | :link: | |
APE | Monkey's Audio | :link: | |
ASF | Advanced Systems Format | :link: | |
DSDIFF | Philips DSDIFF | :link: | |
DSF | Sony's DSD Stream File | :link: | |
FLAC | Free Lossless Audio Codec | :link: | |
MP2 | MPEG-1 Audio Layer II | :link: | |
MP3 | MPEG-1 / MPEG-2 Audio Layer III | :link: | |
MPC | Musepack SV7 | :link: | |
MPEG 4 | mp4, m4a, m4v | :link: | |
Ogg / Opus | :link: | ||
Ogg / Speex | :link: | ||
Ogg / Vorbis | :link: | ||
WAV | RIFF WAVE | :link: | |
WV | WavPack | :link: | |
WMA | Windows Media Audio | :link: |
Following tag header formats are supported:
It allows many tags to be accessed in audio format, and tag format independent way.
Support for MusicBrainz tags as written by Picard. ReplayGain tags are supported.
Support for encoding / format details:git pull
The JavaScript in runtime is compliant with ECMAScript 2017 (ES8). Requires Node.js® version 6 or higher.
Although music-metadata is designed to run the node.js. music-metadata-browser can be used on the browser side.
To avoid Node fs
dependency inclusion, you may use a sub-module inclusion:
import * as mm from 'music-metadata/lib/core';
function | music-metadata | music-metadata/lib/core |
---|---|---|
parseBuffer | ✓ | ✓ |
parseStream * | ✓ | ✓ |
parseFromTokenizer | ✓ | ✓ |
parseFile | ✓ |
Not required, but would be extremely motivating. PayPal.me
Install via npm:
npm install music-metadata
or yarn
yarn add music-metadata
Import music-metadata in JavaScript:
const mm = require('music-metadata');
This is how it's done in TypeScript:
import * as mm from 'music-metadata';
There are two ways to parse (read) audio tracks:
Direct file access tends to be a little faster, because it can 'jump' to various parts in the file without being obliged to read intermediate date.
Parses the specified file (filePath
) and returns a promise with the metadata result (IAudioMetadata
).
parseFile(filePath: string, opts: IOptions = {}): Promise<IAudioMetadata>`
Javascript example:
const mm = require('music-metadata');
const util = require('util')
mm.parseFile('../test/samples/MusicBrainz-multiartist [id3v2.4].V2.mp3', {native: true})
.then( metadata => {
console.log(util.inspect(metadata, { showHidden: false, depth: null }));
})
.catch( err => {
console.error(err.message);
});
Typescript example:
import * as mm from 'music-metadata';
import * as util from 'util';
mm.parseFile('../test/samples/MusicBrainz-multiartist [id3v2.4].V2.mp3')
.then( metadata => {
console.log(util.inspect(metadata, {showHidden: false, depth: null}));
})
.catch((err) => {
console.error(err.message);
});
Parses the provided audio stream for metadata.
It is recommended to provide the corresponding MIME-type.
An extension (e.g.: .mp3
), filename or path will also work.
If the MIME-type or filename is not provided, or not understood, music-metadata will try to derive the type from the content.
parseStream(stream: Stream.Readable, mimeType?: string, opts?: IOptions = {}): Promise<IAudioMetadata>`
Example:
mm.parseStream(someReadStream, 'audio/mpeg', { fileSize: 26838 })
.then( metadata => {
console.log(util.inspect(metadata, { showHidden: false, depth: null }));
someReadStream.destroy();
});
Parse metadata from an audio file, where the audio file is held in a Buffer.
parseBuffer(buffer: Buffer, mimeType?: string, opts?: IOptions = {}): Promise<IAudioMetadata>
Example:
mm.parseBuffer(someBuffer, 'audio/mpeg', { fileSize: 26838 })
.then( metadata => {
console.log(util.inspect(metadata, { showHidden: false, depth: null }));
});
This is a low level function, reading from a strtok3 ITokenizer interface. music-metadata-browser is depended on this function.
This also enables special read modules like:
Utility to Converts the native tags to a dictionary index on the tag identifier
orderTags(nativeTags: ITag[]): [tagId: string]: any[]
Can be used to convert the normalized rating value to the 0..5 stars, where 0 an undefined rating, 1 the star the lowest rating and 5 the highest rating.
ratingToStars(rating: number): number
duration
: default: false
, if set to true
, it will parse the whole media file if required to determine the duration.fileSize
: only provide this in combination with parseStream
function.native
: default: false
, if set to true
, it will return native tags in addition to the common
tags.observer: (update: MetadataEvent) => void;
: Will be called after each change to common
(generic) tag, or format
properties.skipCovers
: default: false
, if set to true
, it will not return embedded cover-art (images).skipPostHeaders? boolean
default: false
, if set to true
, it will not search all the entire track for additional headers. Only recommenced to use in combination with streams.Although in most cases duration is included, in some cases it requires music-metadata
parsing the entire file.
To enforce parsing the entire file if needed you should set duration
to true
.
If the returned promise resolves, the metadata (TypeScript IAudioMetadata
interface) contains:
format: IFormat
Audio format informationnative: INativeTags
List of native (original) tags found in the parsed audio file. If the native option is set to false, this property is not defined.common: ICommonTagsResult
Is a generic (abstract) way of reading metadata information.Audio format information. Defined in the TypeScript IFormat
interface:
container?: string
Audio encoding format. e.g.: 'flac'codec?
Name of the codec (algorithm used for the audio compression)codecProfile?: string
Codec profile / settingstagTypes?: TagType[]
List of tagging formats found in parsed audio fileduration?: number
Duration in secondsbitrate?: number
Number bits per second of encoded audio filesampleRate?: number
Sampling rate in Samples per second (S/s)bitsPerSample?: number
Audio bit depthlossless?: boolean
True if lossless, false for lossy encodingnumberOfChannels?: number
Number of audio channelsnumberOfSamples?: number
Number of samples frames, one sample contains all channels. The duration is: numberOfSamples / sampleRateCommon tag documentation is automatically generated.
In order to read the duration of a stream (with the exception of file streams), in some cases you should pass the size of the file in bytes.
mm.parseStream(someReadStream, 'audio/mpeg', { duration: true, fileSize: 26838 })
.then( function (metadata) {
console.log(util.inspect(metadata, { showHidden: false, depth: null }));
someReadStream.close();
});
How can I traverse (a long) list of files?
What is important that file parsing should be done in a sequential manner. In a plain loop, due to the asynchronous character (like most JavaScript functions), it would cause all the files to run in parallel which is will cause your application to hang in no time. There are multiple ways of achieving this:
Using recursion
const mm = require('music-metadata')
function parseFiles(audioFiles) {
const audioFile = audioFiles.shift();
if (audioFile) {
return mm.parseFile(audioFile).then(metadata => {
// Do great things with the metadata
return parseFiles(audioFiles); // process rest of the files AFTER we are finished
})
}
return Promise.resolve();
}
Use async/await
Use async/await
const mm = require('music-metadata')
// it is required to declare the function 'async' to allow the use of await
async function parseFiles(audioFiles) {
for (const audioFile of audioFiles) {
// await will ensure the metadata parsing is completed before we move on to the next file
const metadata = await mm.parseFile(audioFile);
// Do great things with the metadata
}
}
Use a specialized module to traverse files
There are specialized modules to traversing (walking) files and directory, like walk.
(The MIT License)
Copyright (c) 2017 Borewit
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
FAQs
Music metadata parser for Node.js, supporting virtual any audio and tag format.
The npm package music-metadata receives a total of 241,336 weekly downloads. As such, music-metadata popularity was classified as popular.
We found that music-metadata demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket’s threat research team has detected six malicious npm packages typosquatting popular libraries to insert SSH backdoors.
Security News
MITRE's 2024 CWE Top 25 highlights critical software vulnerabilities like XSS, SQL Injection, and CSRF, reflecting shifts due to a refined ranking methodology.
Security News
In this segment of the Risky Business podcast, Feross Aboukhadijeh and Patrick Gray discuss the challenges of tracking malware discovered in open source softare.